Methods and apparatus for communicating uplink control information

ABSTRACT

Methods and apparatus related to HARQ feedback, e.g. delayed HARQ ACK/NACK, and uplink control information (UCI) multiplexing, in unlicensed spectrum are described. A base station transmits an UCI request to a UE, including: a request for ACK/NACK feedback corresponding to a set of HARQ identified processes, a request for channel state information report, and/or a scheduling request. The UCI request includes information which is used, by the UE, in determining the time and air link resources on which to send the UCI. The HARQ processes are communicated in a first Channel Occupancy Time (COT), while the ACK/NACK feedback is communicated in a later COT.

FIELD

The present application relates to communications methods and apparatus,and more particularly, to methods and apparatus related to HARQfeedback, e.g. delayed HARQ ACK/NACK, and uplink control information(UCI) multiplexing, in unlicensed spectrum.

BACKGROUND

Long Term Evolution (LTE) licensed Assisted Access (LAA) and itsenhancements enhanced LAA/further enhanced LAA (eLAA/FeLAA) wereintroduced in 3GPP Release 13-15 to specify Downlink (DL) and Uplink(UL) LTE operation in unlicensed spectrum, primarily 5GHz. Note thatLTE-LAA does not support uplink control channels.

As future systems and standards are developed for radio communicationsincluding those applicable to 5G, there is a need for methods andapparatus improved methods of controlling what information will betransmitted in the uplink and/or when particular information iscommunicated. As 5G, New Radio (NR) and the use of unlicensed spectrumbecomes of ever greater importance there is a need for new efficientmethods and apparatus for requesting and reporting uplink controlinformation including feedback results, e.g. ACK/NACKs for an identifiedset of HARQ processes transmitted in during a channel occupancy time(COT).

SUMMARY

Various embodiments are directed to methods and apparatus related touplink control information (UCI) requesting and reporting, said UCIincluding Hybrid Automatic Repeat Request acknowledgment/negativeacknowledgment (HARQ ACK/NACKS), channel state information (CSI) reportsand/or scheduling request (SRs). Various embodiments, in accordance withthe present invention are well suited for use in unlicensed spectrum,e.g., new radio—unlicensed (NR-U) in which air link resources may notalways be available or may only be available for short durations. Someembodiments of the present invention are directed to methods andapparatus to control uplink control information (UCI) multiplexing, forexample, such as CSI and/or SR together with HARQ ACK/NACK, e.g.,delayed ACK/NACK, for the new feedback opportunities introduced inREL-16 NR-U. In some embodiments, novel features allow a base station,e.g. a gNB, to control the UCI payload size of the UE and the timing ofthe UCI feedback with greater granularity.

An exemplary communications method, in accordance with some embodiments,comprises: operating a base station, e.g., a gNB, to transmit an uplinkcontrol information (UCI) request in a Physical Downlink Control Channel(PDCCH) to a User Equipment (UE), said UCI request requestingtransmission of HARQ acknowledgment information for one or morepreviously communicated transmission segments identified by HARQ IDsincluded in the UCI request and including an indication of informationto be multiplexed with HARQ acknowledgement information; and operatingthe base station to monitor for uplink control information includingHARQ information from the UE.

An exemplary base station, e.g., gNB, in accordance with someembodiments, comprises a wireless transmitter; a wireless receiver; anda processor configured to: operate the base station to transmit, e.g.,via the wireless transmitter, an uplink control information (UCI)request in a Physical Downlink Control Channel (PDCCH) to a UserEquipment (UE), said UCI request requesting transmission of HARQacknowledgment information for one or more previously communicatedtransmission segments identified by HARQ IDs included in the UCI requestand including an indication of information to be multiplexed with HARQacknowledgement information; and operate the base station to monitor foruplink control information including HARQ information from the UE.

While various features discussed in the summary are used in someembodiments it should be appreciated that not all features are requiredor necessary for all embodiments and the mention of features in thesummary should in no way be interpreted as implying that the feature isnecessary or critical for all embodiments.

Numerous additional features and embodiments are discussed in thedetailed description which follows.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a drawing of an exemplary communications system, whichsupports novel uplink control information (UCI) requests in unlicensedspectrum in a physical downlink control channel (PDCCH) to a UE, inaccordance with an exemplary embodiment.

FIG. 2 is a drawing which includes an exemplary base station, a gNB, anexemplary UE, and exemplary signaling, in accordance with an exemplaryembodiment.

FIG. 3 illustrates drawing of exemplary DCI fields (HARQ IDs Field, CSIRequest Field, Beta Offset Field, TPC command Field, PUCCH resourceindicator field, Timing indicator field, Downlink Assignment indexfield) included in an exemplary UCI request in accordance with anexemplary embodiment.

FIG. 4A is a first part of flowchart of an exemplary communicationsmethod in accordance with an exemplary embodiment.

FIG. 4B is a second part of flowchart of an exemplary communicationsmethod in accordance with an exemplary embodiment.

FIG. 4 comprises the combination of FIG. 4A and FIG. 4B.

FIG. 5 is a drawing including an exemplary base station, e.g. a gNB, anexemplary UE, and exemplary signaling, in accordance with an exemplaryembodiment.

FIG. 6 illustrates drawing of exemplary DCI fields (Indications foractivation of one of CGs field, HARQ IDs being Reported Field,Indication of whether SR should be reported field, CSI Request used tocontrol UCI multiplexing Field, Beta Offset Field, TPC command field,Downlink Assignment index field) included in an exemplary DCI formatmessage used in the case of TYPE II CG to convey an UCI request.

FIG. 7A is a first part of a flowchart of an exemplary communicationsmethod in accordance with an exemplary embodiment.

FIG. 7B is a second part of a flowchart of an exemplary communicationsmethod in accordance with an exemplary embodiment.

FIG. 7 comprises the combination of FIG. 7A and FIG. 7B.

FIG. 8 is a flowchart of an exemplary communications method inaccordance with an exemplary embodiment.

FIG. 9 is a drawing of an exemplary base station, e.g., a gNB or ng-eNB,in accordance with an exemplary embodiment.

FIG. 10 is a drawing of an exemplary user equipment (UE) deviceimplemented in accordance with an exemplary embodiment.

FIG. 11A is a drawing of a first part of an exemplary assembly ofcomponents, which may be included in an exemplary base station inaccordance with an exemplary embodiment.

FIG. 11B is a drawing of a second part of an exemplary assembly ofcomponents, which may be included in an exemplary base station inaccordance with an exemplary embodiment.

FIG. 11C is a drawing of a third part of an exemplary assembly ofcomponents, which may be included in an exemplary base station inaccordance with an exemplary embodiment.

FIG. 11 comprises the combination of FIG. 11A, FIG. 11B and FIG. 11C.

FIG. 12A is a drawing of a first part of an exemplary assembly ofcomponents, which may be included in an exemplary user equipment (UE),in accordance with an exemplary embodiment.

FIG. 12B is a drawing of a second part of an exemplary assembly ofcomponents, which may be included in an exemplary user equipment (UE),in accordance with an exemplary embodiment.

FIG. 12 comprises the combination of FIG. 12A and FIG. 12B.

DETAILED DESCRIPTION

FIG. 1 is a drawing of an exemplary communications system 100, whichsupports novel uplink control information (UCI) requests in unlicensedspectrum in a physical downlink control channel (PDCCH) to a UE, inaccordance with an exemplary embodiment. The UCI request, which in someembodiments is a command, may, and sometimes does, convey a request foridentified HARQ ACK/NACKs, e.g., a request for delayed ACK/NACKs from aUE corresponding to identified HARQ process identifiers included in therequest, a request for a channel state information (CSI) report, and/ora scheduling request (SR). In some embodiments, the UCI request is viadownlink control information (DCI) in the Physical Downlink Controlchannel, and the UCI request is requesting the UE to transmit the HARQacknowledgment in a Physical Uplink Shared Channel (PUSCH). In some suchembodiments, a timing indicator in a timing indicator field of the UCIrequest is used to indicate which slot to transmit the UCI. In someembodiments, the UCI request is via downlink control information (DCI)addressed to a Configured Scheduling-Radio Network Temporary Identifier(CS-RNTI) in the Physical Downlink Control channel (PDCCH), and the UCIrequest is requesting the UE to transmit HARQ acknowledgment in theConfigured Grant Physical Uplink Shared Channel (PUSCH). In some suchembodiments, indicators included in an activation field are used foractivating one of the configured grants, which is used to identifyuplink resources to be used to communicate the UCI.

Exemplary communications system 100 includes a network node 102, e.g., acore network node, a plurality of base stations (base station 1 104,e.g., gNB 1 or ng-eNB 1, base station 2 106, e.g., gNB 2 or ng-eNB 2, .. . , base station n 108, e.g., gNBn or ng-eNBn), and a plurality ofuser equipment (UE) devices (UE 1 110, UE 2 112, UE 3 114, UE 4 116, UE5 118, UE 6 120, . . . , UE N 122). Each of the base stations (basestation 1 104, base station 2 106, . . . , base station n 108) has acorresponding wireless coverage area (105, 107, . . . , 109),respectively. Network node 102 is coupled to base station 1 104 viacommunications connection 124. Network node 102 is coupled to basestation 2 106 via communications connection 126. Network node 102 iscoupled to base station n 108 via communications connection 128. Thebase stations (104, 106, . . . , 108) use unlicensed spectrum. In someembodiments, the different base stations (104, 106, . . . , 108) usedifferent bandwidth portions, e.g., different non-overlapping bandwidthportions, of unlicensed spectrum. In some embodiments, a bandwidthportion of unlicensed spectrum is 20 MHz. In some embodiments, abandwidth portion of unlicensed spectrum includes a plurality ofsub-bands. In some such embodiments, each sub-band in a bandwidthportion is 20 MHz.

At least some of the UE devices (110, 112, 114, 116, 118, 120, . . . ,122) are mobile devices which may move throughout the communicationssystem 100. In the drawing of FIG. 1, UE 1 110 and UE 2 112 are shown tobe currently within the wireless coverage area 105 of base station 1104. UE 3 114 is shown to be currently outside the coverage areas (105,107, 109) of the base stations. UE 4 116 and UE 5 118 are shown to becurrently within the wireless coverage area 107 of base station 2 106.UE 6 120 and UE N 122 are shown to be currently within the wirelesscoverage area 109 of base station 3 108.

In some exemplary embodiments, a downlink indication (e.g. downlinkcontrol information or DCI) that triggers a delayed HARQ ACK/NACKfeedback from a UE also includes one or more bits to indicate whetherand what form of CSI feedback can be multiplexed in the same feedbackinstance. In one example, the UE may transmit the indicated informationon Physical Uplink Control Channel (PUCCH), as shown in FIG. 2, wherethe Downlink Control Information (DCI) in the last slot of COT nprovides the timing and multiplexing information for the feedback in COTn+1. In another example, the indicated UCI may be multiplexed with aPUSCH transmission for which the UE has received an uplink grant.

Furthermore, a gnB may change the beta offset to increase channelredundancy for the UCI, and/or may change associated indications withinthe DCI so the UE either sends the delayed HARQ A/Ns only or multiplexesa partial CSI report (e.g., CSI part 1 only).

FIG. 2 is a drawing 200 which includes an exemplary base station, gNB202, an exemplary UE 204, and exemplary signaling 205, in accordancewith an exemplary embodiment. Horizontal axis 201 represents time.Exemplary UE 204 is, e.g., UE 110 of FIG. 1 or UE 1000 of FIG. 10.Exemplary base station 202 is, e.g., base station 104 of FIG. 1 or basestation 900 of FIG. 9. Exemplary gNB 202 performs LTB 206, followed byPDSCH 208 and PDSCH 212. PDSCH 208 communicates HARQ ID x process 210and PDSCH 212 communicates HARQ ID y process 214, which are included inCOT n 216. The DCI 217 in the Physical Downlink Control Channel 2171 ofthe last slot of COT n 216 communicates the UCI request including timingand multiplexing information for the feedback to be in COT n+1 226, asindicated by arrow 218 and block 224.

In COT n+1 226, UE 204, performs LBT 220 and then transmits UCI in PUCCH222, which, communicates HARQ ACK/NACK for x, + a CSI report, asindicated by block 224.

FIG. 3 illustrates drawing 300 of exemplary DCI fields (HARQ IDs Field302, CSI Request Field 304, Beta Offset Field 306, TPC command Field308, PUCCH resource indicator field 310, Timing indicator field 312,Downlink Assignment index field 314) included in an exemplary UCIrequest in accordance with an exemplary embodiment.

A non-limiting example of the contents of an exemplary DCI Format usedto control UCI multiplexing, in some embodiments, is provided in FIG. 3and described in detail below. It should be understood that this is nota comprehensive list of all potential fields of such a DCI format.

DCI fields:

HARQ IDs for which ACK/NACK should be reported (e.g., up to 16 bits if abitmap is used with one bit per DL HARQ ID) are included in the HARQ IDfield 302.

CSI request used to control UCI multiplexing (e.g., up to 6 bits thatmay further be mapped to a pre-configured look-up table) is included inthe CSI request field 304.

Beta offset to control UCE error control coding (e.g., 2 bits) isincluded in the Beta offset field 306

Transmit Power Control (TPC) command for PUCCH carrying delayed ACK/NACKand other UCI (e.g. 2 bits) is conveyed in the TOC command field 308.

PUCCH resource indicator (e.g., up to 3 bits) is conveyed in the PUCCHresource field.

Timing indicator for which slot to transmit the UCE (e.g., up to 4 bits)is conveyed in the timing indicator field 312.

Downlink Assignment index (e.g., 2 bits or 4 bits) is conveyed in thedownlink assignment index field 314.

FIG. 4, comprising the combination of FIG. 4A and FIG. 4B, is aflowchart 400 of an exemplary communications method in accordance withan exemplary embodiment. Flowchart 400 depicts exemplary base station,e.g. gNB,—user equipment (UE) interactions, e.g., base station 1 104 andUE 1 110 interactions, in accordance with an exemplary embodiment.Operation of the exemplary method starts in step 402 in which thecommunications system, e.g. communications system 100 of FIG. 1, ispowered on and initialized, e.g., communications devices including basestation 1 104 and UE 1 110 are powered on and initialized. Operationproceeds from step 402 to step 404.

In step 404, the base station, e.g. gNB, configures a user equipment(UE) with a Physical Uplink Control Channel (PUCCH) resource set fordelayed ACK/NACK feedback and a look-up table for Uplink ControlInformation (UCI) multiplexing rules. Step 404 includes step 406 inwhich the base station, e.g., gNB, transmits to the UE configurationinformation, said configuration information including a PUCCH resourceset for delayed ACK/NACK feedback and a look-up table for UCImultiplexing rules. Operation proceeds from step 404 to step 408.

In step 408 the UE receives from the base station said configurationinformation, said configuration information including a PUCCH resourceset for delayed ACK/NACK feedback and a look-up table for UCImultiplexing rules. Operation proceeds from step 408 to step 410. Instep 410 the UE stores the received configuration information. Operationproceeds from step 410 to step 412.

In step 412 the base station, e.g. gNB, performs downlink (DL)listen-before-talk (LBT) and transmits a first set of DL HARQ processeson Physical Downlink Shared Channel (PDSCH). Operation proceeds fromstep 412 to step 414.

In step 414 the base station, e.g. gNB, transmits uplink controlinformation (UCI) request for the first set of DL HARQ processes viaDownlink Control Information (DCI) on Physical Downlink Control Channel(PDCCH) in a later set of DL transmissions. Step 414 includes steps 416,and 426, and in some embodiments, includes one or more or all of steps418, 420, 422, 424, and 428. In step 416 the base station includes HARQIDs in the UCI request indicating HARQs for which ACK/NACK should bereported. In step 426 the base station includes, in the UCI request, atiming indicator indicating which slot to transmit the UCI. In step 418the base station includes in the UCI request, a CS request used tocontrol UCI multiplexing. In step 420 the base station includes, in theUCI request, a BETA offset used to control UCI error coding. In step 422the base station includes, in the UCI request, a transmit power control(TPC) command for PUSCH carrying the delayed ACK/NACK and other UCI. Instep 424 the base station includes, in the UCI request, a PUCCH resourceindicator. In step 428 the base station includes, in the UCI request, adownlink timing index. Operation proceeds from step 414 to step 430.

In step 430 the UE receives the UCI request for the first set of DL HARQprocesses via DCI on PDCCH in a later set of DL transmissions. In someembodiments, the UCI request is communicated in the same COT as the HARQprocesses for which ACK/NACK is being requested, e.g., at the end of theCOT, e.g., as shown in FIG. 2. In some embodiments, the UCI request iscommunicated in a different COT than the COT in which the HARQ processesfor which ACK/NACK is being requested, e.g., the next COT. Operationproceeds from step 430 to step 432.

In step 432 the UE determines when to perform UCI transmissions based oninformation, e.g. the timing indicator, e.g., included in the receivedUCI request, e.g., the timing indicator included in timing indicatorfield 312 of FIG. 3. Operation proceeds from step 432 to step 434.

In step 434 the UE determines uplink control information (UCI) contentsto be transmitted in response to the DCI. Operation proceeds from step434 to step 436.

In step 436 the UE performs uplink control information (UCI)transmissions as per parameters includes in Downlink Control Information(DCI) of the received UCI request, e.g. communicating the requestedinformation at the timing indicator indicated time. Step 436 includesstep 438, in which the base station transmits ACK/NACKs corresponding toHARQ IDs. In some embodiments, step 426 may, and sometimes does, includestep 440, in which the base station transmit a channel state information(CSI) report. Operation proceeds from step 436 to step 442.

In step 442 the base station monitors for and/or receives UCItransmissions including HARQ information at the time corresponding tothe timing indicator in the UCI request. Thus in step 442 the basestation monitors for and/or receives uplink control informationincluding HARQ information from the UE. Operation proceeds from step 442to the input of step 412.

In some embodiments, the delayed ACK/NACK feedback that is potentiallymultiplexed with other UCI is transmitted on a configured grant (CG)Physical Uplink Shared Channel (PUSCH), with or without uplink-sharedchannel (UL-SCH). The parameters for a CG PUSCH transmission (such astime-frequency resources, periodicity, Modulation and Coding Scheme(MCS), etc.) are wholly (Type 1 CG) or partially (Type II) pre-definedby higher layer signaling.

For Type I CG, the UCI multiplexing rules may be, and sometimes are,defined semi-statically where the configured grant (CG) is configured.

For a type-II CG, in accordance with a feature of some novelembodiments, the triggering Downlink Control Information (DCI) addressedto Configured Scheduling—Radio Network Temporary Identifier (CS-RNTI)also indicates what kind of uplink control information (UCI)multiplexing may be performed on the CG PUSCH for ACK/NACK feedbackcorresponding to a previous COT, as shown in FIG. 5.

For both types of CG, the CG-UCI accompanying the PUSCH may indicate tothe base station, e.g. gNB, whether the CG PUSCH has been multiplexedwith UCI, and what are the contents of said UCI.

FIG. 5 is a drawing 500 including an exemplary base station, gNB 502, anexemplary UE 504, and exemplary signaling 505, in accordance with anexemplary embodiment. Horizontal axis 501 represents time. Exemplary UE504 is, e.g., UE 110 of FIG. 1 or UE 1000 of FIG. 10. Exemplary basestation 502 is, e.g., base station 104 of FIG. 1 or base station 900 ofFIG. 9. Exemplary gNB 502 performs LTB 506, followed by PDSCH 508 andPDSCH 512. PDSCH 508 communicates HARQ ID x process 510 and PDSCH 512communicates HARQ ID y process 514, which are included in COT n 516.

Exemplary gNB 502 performs LTB 518, followed by PDCCH 520, whichcommunicates DCI to CS-RNTI 522, conveying an UCI request, which isincluded in COT n+1 524.

In COT n+2 526, UE 504, performs LBT 528 and then transmits UCI in CGPUSCH 529, which, communicates HARQ ACK/NACK for x, +a schedulingrequest (SR) + a CSI report, as indicated by block 530.

Furthermore, in the case of NACK for CG PUSCH that carries delayed HARQAcknowledgment/Negative Acknowledgment (A/N)s, Scheduling Request (SR)and Channel State Information (CSI) report, the UE may, and sometimesdoes, change the beta offset to increase channel redundancy for UCIand/or may, and sometimes does, change associated indications with theUCI so that the UE either sends the delayed HARQ A/Ns only ormultiplexes a partial CSI report. The above change in UCI multiplexingrules (in case of NACK) may be semi-statically defined or may beindicated within the DCI addressed to CS-RNTI; otherwise, the CG-UCIaccompanying the PUSCH indicates whether CSI has been multiplexed.

For Type 1 CG, the changes in the RRC configuration [TS 38.331] for theConfiguredGrantConfig information element are exemplified below:

 CG-UCI-ONPUSCH::= Choice {   dynamic SEQUENCE (SIZE (1..4) OFBetaOffsets,   semi Static BetaOffsets  UCI multiplexing ENUMERATED{HARQ ACK-NACK only, ACK-NACK and CSI part 1, ACK-NACK and CSI part 1and part 2}  MaxUCI payload INTEGER {1 . . . 128}  }

The parameters for a CG PUSCH transmission are partially pre-defined byhigher-layer signaling in case of CG Type II, and the remainingparameters are defined by a DCI.

A non-limiting example of the contents of a DCI format used in the caseof Type II CG to control UCI multiplexing in this exemplary embodimentis described below and shown in FIG. 6. It should be understood thatthis is not a comprehensive list of all potential fields if a DCIformat. The DCI is addressed to CS-RNTI.

DCI fields for type II CG (in addition to parameters in the baselinespec):

Indications for activation of one of the CGs (e.g., 2 bits if four setsof CG PUSCHs are configured for a UE) are included in Indications foractivation of one of CGs field 602.

HARQ IDs being reported (e.g., up to 16 bits if a bitmap is used withone bit per DL HARQ ID) are included in HARQ IDs being Reported Field604.

Indication of whether Scheduling Request (SR) should be reported (1 bit)is included in Indication of whether SR should be reported field 606.

CSI request used to control UCI multiplexing (e.g., up to 6 bits thatmay further be mapped to a pre-configured look-up table) is included inCSI Request used to control UCI multiplexing Field 608.

Beta offset to control UCE error control coding (e.g., 2 bits) isincluded in Beta offset field 610.

Transmit Power Control (TPC) command for CG PUSCH carrying delayedACK/NACK and other UCI (e.g., 2 bits) is included in TPC command field612.

Downlink assignment index (e.g., 2 bits or 4 bits) is included inDownlink assignment index field 614.

FIG. 6 illustrates drawing 600 of exemplary DCI fields (Indications foractivation of one of CGs field 602, HARQ IDs being Reported Field 604,Indication of whether SR should be reported field 606, CSI Request usedto control UCI multiplexing Field 608, Beta Offset Field 610, TPCcommand field 612, Downlink Assignment index field 614) included in anexemplary DCI format message used in the case of TYPE II CG to convey anUCI request.

FIG. 7, comprising the combination of FIG. 7A and FIG. 7B, is aflowchart 700 of an exemplary communications method in accordance withan exemplary embodiment. Flowchart 700 depicts base station, e.g.gNB,—user equipment (UE) interactions, e.g., base station 1 104-UE 1 110interactions, in accordance with an exemplary embodiment. Operation ofthe exemplary method starts in step 702 in which the communicationssystem, e.g. communications system 100 of FIG. 1, is powered on andinitialized, e.g., communications devices including base station 104 andUE 110 are powered on and initialized. Operation proceeds from step 702to step 704.

In step 704, the base station, e.g. gNB, configures user equipments(UEs) with: i) sets of Configured Grant Physical Uplink Control Channel(CG PUCCH) resource and ii) look-up table for Uplink Control Information(UCI) multiplexing rules. Step 704 includes step 706 in which the basestation, transmits to a UE configuration information, said configurationinformation including sets of Configured Grant Physical Uplink ControlChannel (CG PUCCH) resource and ii) look-up table for Uplink ControlInformation (UCI) multiplexing rules. Operation proceeds from step 704to step 708.

In step 708 the UE receives from the base station configurationinformation, said configuration information including sets of ConfiguredGrant Physical Uplink Control Channel (CG PUCCH) resource and ii)look-up table for Uplink Control Information (UCI) multiplexing rules.Operation proceeds from step 708 to step 710.

In step 710 the UE stores the received configuration information.Operation proceeds from step 710 to step 712.

In step 712 the base station, e.g. gNB, performs downlink (DL)listen-before-talk (LBT) and transmits a first set of DL HARQ processeson Physical Downlink Shared Channel (PDSCH). Operation proceeds fromstep 712 to step 714.

In step 714 the base station, e.g. gNB, transmits an uplink controlinformation (UCI) request for the first set of DL HARQ processes viaDownlink Control Information (DCI) (addressed to ConfiguredScheduling—Radio Network Temporary Identifier (CS-RNTI)) on PhysicalDownlink Control Channel (PDCCH) in a later set of DL transmissions. Insome embodiments, the DL HARQ processes for which ACK/NACK is beingrequested are communicated in a first COT and the UCI request iscommunicated on a second COT, e.g. as shown in FIG. 5.

Step 714 includes steps 716, 718 and 728. In some embodiments, step 714includes one or more or all of steps 720, 722, 724 and 726. In step 716the base station includes, in the UCI request, an indicator foractivation of one of the CGs. In step 718 the base station includes, inthe UCI request, HARQ IDs indicating HARQs for which ACK/NACK should bereported. In step 728 the base station includes a downlink assignmentindex in the UCI request. In step 720 the base station includes, in theUCI request an indication of whether e a scheduling request (SR) shouldbe reported. In step 722 the base station includes, in the UCI request,a CIS request used to control multiplexing. In step 724, the basestation includes, in the UCI request, a beta offset used to controlerror control coding. In step 726 the base station includes, in the UCIrequest, a transmit power control (TPC) command for CG PUSCH carryingdelayed ACK/NACK and other UCI. Operation proceeds from step 714 to step730.

In step 730 the UE receives the UCI request for the first set of DL HARQprocesses via DCI, addressed to CS-RNTI, on PDCCH in a later set oftransmissions. Operation proceeds from step 730, via connecting node A7301, to step 731 in which the UE determines when to perform UCItransmission based on information, e.g., the indicator indicating theone of the CGs, which corresponds to a configured set of CG PUSCHresources, included in the received UCI request. Operation proceeds fromstep 731 to step 732.

In step 732 the UE determines uplink control information (UCI) contentsto be transmitted in response to the DCI. Operation proceeds from step732 to step 734.

In step 734 the UE performs uplink control information (UCI)transmissions as per parameters includes in Downlink Control Information(DCI). Step 734 includes step 736 in which the UE transmits ACK/NACKscorresponding to the HARQ IDs in the UCI request. Step 734 may, andsometimes does, include one or both of steps 738 and step 740. In step738 the UE transmits a scheduling request (SR). In step 740 the UEtransmits a CSI report. Operation proceeds from step 734 to step 744.

In step 744 the base station monitors for and/or receives UCItransmissions based on information included in the UCI request. Thus instep 744 the base station monitors for and/or receives uplink controlinformation including HARQ information from the UE.Operation proceedsfrom step 744, via connecting node B 746, to the input of step 712.

Another exemplary embodiment is an extension of an embodimentcorresponding to FIG. 4, in which the embodiment of FIG. 4 is extendedto cover wideband operation on a carrier wider than 20 MHz. Anotherexemplary embodiment is an extension of an embodiment corresponding toFIG. 7, in which the embodiment of FIG. 7 is extended to cover widebandoperation on a carrier wider than 20 MHz.

In one non-limiting example, the DL indication form the base station,e.g. gNB may, and sometimes does, also indicate one or more sub-bands onwhich the UE may attempt UL LBT, in addition to the UCI multiplexinginformation discussed previously.

In another example, example, the UE autonomously chooses whether tomultiples the delayed HARQ ACk/NACK feedback with other UCI dependingupon the number of LBT sub-bands it has passed UL LBT on, which dictatesthe quantum of frequency-domain resources it has available fortransmission. In a further aspect, of some embodiments, the UE may, andsometimes does, multiples additional control information related to thequality or channel occupancy of individual sub-bands constituting thewideband carrier.

FIG. 8 is a flowchart 800 of an exemplary communications method inaccordance with an exemplary embodiment. Flowchart 800 depicts basestation, e.g. gNB,—user equipment (UE) interactions, e.g., base station104 -UE 110 interactions, in accordance with an exemplary embodiment.Operation of the exemplary method starts in step 802 in which thecommunications system, e.g. communications system 100 of FIG. 1, ispowered on and initialized. Operation proceeds from step 802 to step804.

In step 804, the base station, e.g. gNB, configures user equipments(UEs) with either: i) PUCCH resource set for delayed or ii) sets of GCPUSCH resource, where these resources may be on a carrier wider than 20MHz; base station, e.g. gNB, also configured the UE(s) with look-uptable for Uplink Control Information (UCI) multiplexing rules. Operationproceeds from step 804 to step 806.

In step 806 the base station, e.g. gNB, performs downlink (DL)listen-before-talk (LBT) and transmits a first set of DL HARQ processeson Physical Downlink Shared Channel (PDSCH). Operation proceeds fromstep 806 to step 808.

In step 808 the base station, e.g. gNB, transmits uplink controlinformation (UCI) request for the first set of DL HARQ processes viaDownlink Control Information (DCI) on Physical Downlink Control Channel(PDCCH) in a later set of downlink transmissions, wherein the DCI may:i) be addressed to Configured Scheduling—Radio Network TemporaryIdentifier (CS-RNTI)); ii) indicate one or more LBT sub-bands. Operationproceeds from step 808 to step 810.

In step 810 the UE determines uplink control information (UCI) contentsto be transmitted in response to the UCI request. In step 810, the UEdevice determines control information related to channel quality orchannel occupancy to multiplex and transmit with HARQ acknowledgementinformation in response to the UCI Request. Operation proceeds from step810 to step 812.

In step 812 the UE performs uplink control information (UCI)transmissions as per parameters included in Downlink Control Information(DCI) given the number of sub-bands with successful LBT; UE may, andsometimes does, add additional control information related to thequality and/or channel occupancy of individual sub-bands constitutingthe wideband carrier. In step 812 the UE may, and sometimes does,transmit said determined control information related to channel qualityor channel occupancy multiplexed with the determined HARQacknowledgement information. Operation proceeds from step 812 to step814.

In step 814 the base station monitors for and/or receives UCItransmissions based on information included in the UCI request. Thus instep 714 the base station monitors for and/or receives uplink controlinformation including HARQ information from the UE. Operation proceedsfrom step 814 to the input of step 806.

FIG. 9 is a drawing of an exemplary base station 900, e.g., a gNB orng-eNB, in accordance with an exemplary embodiment. In some embodiments,exemplary base station 900 of FIG. 9 implements: steps of the exemplarymethod of flowchart 400 of FIG. 4, steps of the exemplary method offlowchart 700 of FIG. 7, and/or steps of the exemplary method offlowchart 800 of FIG. 8. Base station 900 is, e.g., any of base stations(base station 1 104, base station 2 106, . . . , base station n 108) ofFIG. 1.

Base station 900 includes a processor 902, e.g. a CPU, wirelessinterface 904, a network interface 906, e.g., a wired or opticalinterface, an assembly of hardware components 908, e.g., an assembly ofcircuits, and memory 910 coupled together via a bus 911 over which thevarious elements may interchange data and information.

Network interface 906 includes a receiver 916 and a transmitter 918.Network interface 906 to coupled to network nodes, e.g., via a backhaulnetwork and/or the Internet. Wireless interface 904 includes a wirelessreceiver 912 and a wireless transmitter 914. The base station 900receives signals from network devices, e.g. core network devices.Wireless receiver 912 is coupled to a receive antenna 913 via which thebase station 900 can receive wireless signals, e.g., wireless signalsfrom UE devices. Wireless transmitter 914 is coupled to a transmitantenna 915 via which the base station 900 can transmit wireless signalsto UE devices.

Memory 910 includes a control routine 920, e.g., for controlling basicfunctions of the base station, an assembly of components 922, e.g., anassembly of software components, and data/information 924.Data/information 924 includes unlicensed spectrum information 926,configuration information to be sent to the UE 928, e.g., PUCCH resourcesets, sets of CG PUCCH resource sets, and look-up tables for UCImultiplexing rules, LBT results 930, HARQ process transmission signals932, e.g., generated UCI request 934, e.g., including DCI fields asshown in FIG. 3 and/or FIG. 6, and received UCI from UE 936.

FIG. 10 is a drawing of an exemplary user equipment (UE) device 1000implemented in accordance with an exemplary embodiment. UE device 1000is, e.g. one of the UE devices (110, 112, 114, 116, 118, 120, 122) ofsystem 100 of FIG. 1. UE device 1000 includes a processor 1002, awireless interface 1004, a network interface 1010, an I/O interface1016, an assembly of hardware components 1018, e.g., an assembly ofcircuits, and memory 1020 coupled together via a bus 1022 over which thevarious elements may interchange data and information. Wirelessinterface 1004 includes a wireless receiver 1038 coupled to receiveantenna 1039, via which the UE may receive wireless signals, e.g.,wireless downlink signals from a base station, e.g., a gNB. Wirelessinterface 1004 includes a wireless transmitter 1040 coupled to transmitantenna 1041, via which the UE may transmit wireless signals, e.g.,wireless uplink signals to a base station, e.g., a gNB. Networkinterface 1010, e.g., a wired or optical interface 1010 includes areceiver 1088 and a transmitter 1090.

UE device 1000 further includes a microphone 1024, a speaker 1026,switches 1028, a mouse 1034, a keypad 1032, a display 1030 and a camera1036 coupled to I/O interface 1016, via which the various input/outputdevices (1024, 1026, 1028, 1030, 1032, 1034, 1036) may communicate withthe other elements (1002, 1004, 1010, 1018, 1020) of the UE device.Memory 1020 includes a control routine 1052, an assembly of components1054, e.g., an assembly of software components, and data/information1056.

Data/information 1056 includes received configuration information frombase station 1058, received HARQ process transmission signals 1060,determined HARQ process transmission success/fail results 1062, receivedUCE request from base station 1064, determined time to perform UCEtransmissions 1066, determined contents to include in UCE 1068,generated UCI signals 1070 and unlicensed spectrum information 1070.Generated UCI signals 1070 include ACK/NACKs 1072. Generated UCI signals1070 may include SR 1074 and/or CSI report 1076, e.g., multiplexed withthe HARQ ACK/NACKS in the UCI.

FIG. 11, comprising the combination of FIG. 11A, FIG. 11B and FIG. 11C,is a drawing of an exemplary assembly of components 1100, comprisingPart A 1101, Part B 1103 and Part C 1105, in accordance with anexemplary embodiment. Exemplary assembly of components 1100 which may beincluded in a base station, e.g., a gNB or an ng-eNB, such as theexemplary base station 900, e.g., a gNB or ng-eNB, of FIG. 9, andimplement steps of an exemplary method, e.g., steps of the method of theflowchart 400 of FIG. 4, steps of the method of the flowchart 700 ofFIG. 7, and/or steps of the method of the flowchart 800 of FIG. 8.

Assembly of components 1100 can be, and in some embodiments is, used inbase station 900, e.g., a gNB or ng-eNB, of FIG. 9, base station 1 104of FIG. 1, base station 2 106 of FIG. 1 and/or base station n 108 ofFIG. 1. The components in the assembly of components 1100 can, and insome embodiments are, implemented fully in hardware within the processor902, e.g., as individual circuits. The components in the assembly ofcomponents 1100 can, and in some embodiments are, implemented fully inhardware within the assembly of components 908, e.g., as individualcircuits corresponding to the different components. In other embodimentssome of the components are implemented, e.g., as circuits, within theprocessor 902 with other components being implemented, e.g., as circuitswithin assembly of components 908, external to and coupled to theprocessor 902. As should be appreciated the level of integration ofcomponents on the processor and/or with some components being externalto the processor may be one of design choice. Alternatively, rather thanbeing implemented as circuits, all or some of the components may beimplemented in software and stored in the memory 910 of the base station900, e.g., a gNB or ng-eNB, with the components controlling operation ofthe base station to implement the functions corresponding to thecomponents when the components are executed by a processor, e.g.,processor 902. In some such embodiments, the assembly of components 1100is included in the memory 910 as assembly of components 922. In stillother embodiments, various components in assembly of components 1100 areimplemented as a combination of hardware and software, e.g., withanother circuit external to the processor 902 providing input to theprocessor 902 which then under software control operates to perform aportion of a component's function. While processor 902 is shown in theFIG. 9 embodiment as a single processor, e.g., computer, it should beappreciated that the processor 902 may be implemented as one or moreprocessors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 902, configure the processor 902 to implementthe function corresponding to the component. In embodiments where theassembly of components 900 is stored in the memory 910, the memory 910is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 902, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 11 control and/or configure the base station 900, orelements therein such as the processor 902, to perform the functions ofcorresponding steps illustrated and/or described in the method of one ormore of the flowcharts, signaling diagrams and/or described with respectto any of the Figures. Thus the assembly of components 1100 includesvarious components that perform functions of corresponding one or moredescribed and/or illustrated steps of an exemplary method, e.g., stepsof: the method of flowchart 400 of FIG. 4, the method of flowchart 700of FIG. 7, and/or the method the method of flowchart 800 of FIG. 8and/or described or shown with respect to any of the other figures.

Assembly of components 1100 includes a component 1104 configured tooperate a base station, e.g., a gNB to configure a user equipment (UE)with PUCCH resource set for delayed ACK/NACK feedback and look-up tablefor UCI multiplexing rules. Component 1104 includes a component 1106configured to operate the base station, e.g., gNB, to transmit to the UEconfiguration information, said configuration information including aPUCCH resource set for delayed ACK/NACK feedback and a look-up table forUCI multiplexing rules. Assembly of components 1100 further includes acomponent 1112 configured to operate the base station, e.g., gNB toperform downlink (DL) listen-before-talk (LBT) and transmit a first setof DL HARQ processes on PDSCH. Assembly of components 1100 furtherincludes a component 1114 configured to operate the base station, e .g.gNB to transmit UCI request for first set of DL HARQ processes via DCIon PDCCH in a later set of DL transmissions. Component 1114 includes acomponent 1116 configured to include in the UCI request HARQ IDsindicating HARQs for which ACK/NACK should be reported, a component 1118configured to include in the UCI request a CSI request used to controlUCI multiplexing, a component 1120 configured to include in the UCIrequest a beta offset used to control UCI error coding, a component 1124configured to included in the UCI request a transmit power control (TPC)command for PUSCH carrying delayed ACK/NACK and other UCI, a component1124 configured to include in the UCI request a timing indicatorindicating which slot to transmit the UCI, and a component 1128configured to include in the UCI request a downlink timing index.Assembly of components 1100 further includes a component 1142 configuredto operate the base station to monitor for and/or receive UCItransmission at the time corresponding to the timing indicator in theUCI request. Component 1142 is configured to operate the base station tomonitor for and/or receive uplink control information including HARQinformation from the UE.

Assembly of components 1100 further includes a component 1204 configuredto operate a base station, e.g., a gNB to configure user equipments(UEs) with: i) set of CG PUCCH resource and ii) look-up table for UCImultiplexing rules. Component 1204 includes a component 1206 configuredto operate the base station, e.g., gNB, to transmit to the UEconfiguration information, said configuration information including: i)sets of CG aPUCCH resource; and ii) look-up table for UCI multiplexingrules. Assembly of components 1100 further includes a component 1212configured to operate the base station, e.g., gNB to perform downlink(DL) listen-before-talk LBT) and transmit a first set of DL HARQprocesses on PDSCH. Assembly of components 1100 further includes acomponent 1214 configured to operate the base station, e.g. gNB totransmit UCI request for first set of DL HARQ processes via DCI,addressed to configured scheduling - radio network temporary identifier(CS-RNTI) on PDCCH in a later set of DL transmissions. Component 1214includes a component 1216 configured to include, in the UCI request, anindicator for activation of one of the configured grants (CGs), acomponent 1218 configured to include in the UCI request HARQ IDsindicating HARQs for which ACK/NACK should be reported, a component 1220configured to include, in the UCI request, an indicator of whetherscheduling request (SR) should be reported, a component 1222 configuredto include in the UCI request a CSI request used to control UCImultiplexing, a component 1224 configured to include in the UCI requesta beta offset used to control UCI error control coding, a component 1126configured to included in the UCI request a transmit power control (TPC)command for CG PUSCH carrying delayed ACK/NACK and other UCI, and acomponent 1228 configured to include in the UCI request a downlinkassignment index. Assembly of components 1100 further includes acomponent 1244 configured to operate the base station to monitor forand/or receive UCI transmission based on the information included in theUCI request. Component 1244 is configured to operate the base station tomonitor for and/or receive uplink control information including HARQinformation from the UE.

Assembly of components 1100 further includes a component 1304 configuredto operate a base station, e.g., a gNB, to configure user equipment(s)(UE(s)) with either: i) PUCCH resource set for delay, or ii) sets of CGPUCCH resource, where the resources may be on a carrier wider than 20MHz. Component 1304 is also configured to configured the UE(s) withlook-up table for UCI multiplexing rules. Assembly of components 1100further includes a component 1306 configured to operate the basestation, e.g., gNB to perform listen-before-talk (LBT) and transmitfirst set of DL HARQ processes on PDSCH, a component 1308 configured tooperate the base station, e.g. gNB, to transmit UCI request for firstset of DL HARQ processes via DCI on PDCCH in a later set of DLtransmission. Component 1308 is configured to, in some embodiments,address the DCI in CS-RNTI and ii) indicate one of more LBT sub-bands,and a component 1314 configured to operate the base station to monitorfor and.or receive UCI transmissions based on information included inthe UCI request. Component 1314 is configured to operate the basestation to monitor for and/or receive uplink control informationincluding HARQ information from the UE.

FIG. 12, comprising the combination of FIG. 12 and FIG. 12B, is adrawing of an exemplary assembly of components 1200, comprising Part A1201 and Part B 1203, in accordance with an exemplary embodiment.Exemplary assembly of components 1200 which may be included in a userequipment (UE) device, e.g., UE device 1000 of FIG. 10, and implementsteps of an exemplary method, e.g., steps of the method of the flowchart400 of FIG. 4, steps of the method of the flowchart 700 of FIG. 7,and/or steps of the method of the flowchart 800 of FIG. 8.

Assembly of components 1200 can be, and in some embodiments is, used inUE device 1000 of FIG. 10, or any of the UEs of FIG. 1, e.g. UE 110 ofFIG. 1. The components in the assembly of components 1200 can, and insome embodiments are, implemented fully in hardware within the processor1002, e.g., as individual circuits. The components in the assembly ofcomponents 1200 can, and in some embodiments are, implemented fully inhardware within the assembly of components 1018, e.g., as individualcircuits corresponding to the different components. In other embodimentssome of the components are implemented, e.g., as circuits, within theprocessor 1002 with other components being implemented, e.g., ascircuits within assembly of components 1018, external to and coupled tothe processor 1002. As should be appreciated the level of integration ofcomponents on the processor and/or with some components being externalto the processor may be one of design choice. Alternatively, rather thanbeing implemented as circuits, all or some of the components may beimplemented in software and stored in the memory 1020 of the UE device1000, with the components controlling operation of the UE device toimplement the functions corresponding to the components when thecomponents are executed by a processor, e.g., processor 1002. In somesuch embodiments, the assembly of components 1200 is included in thememory 1020 as assembly of components 1054. In still other embodiments,various components in assembly of components 1200 are implemented as acombination of hardware and software, e.g., with another circuitexternal to the processor 1002 providing input to the processor 1002which then under software control operates to perform a portion of acomponent's function. While processor 1002 is shown in the FIG. 10embodiment as a single processor, e.g., computer, it should beappreciated that the processor 1002 may be implemented as one or moreprocessors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 1002, configure the processor 1002 toimplement the function corresponding to the component. In embodimentswhere the assembly of components 1200 is stored in the memory 1020, thememory 1020 is a computer program product comprising a computer readablemedium comprising code, e.g., individual code for each component, forcausing at least one computer, e.g., processor 1002, to implement thefunctions to which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 12 control and/or configure the UE 1000, or elementstherein such as the processor 1002, to perform the functions ofcorresponding steps illustrated and/or described in the method of one ormore of the flowcharts, signaling diagrams and/or described with respectto any of the Figures. Thus the assembly of components 1200 includesvarious components that perform functions of corresponding one or moredescribed and/or illustrated steps of an exemplary method, e.g., stepsof: the method of flowchart 400 of FIG. 4, the method of flowchart 700of FIG. 7, and/or the method the method of flowchart 800 of FIG. 8and/or described or shown with respect to any of the other figures.

Assembly of components 1200 includes a component 1108 configured tooperate the UE to receive from the base station, e.g., a gNBconfiguration information, said configuration information including aPUCCH resource set for delayed ACK/NACK feedback and a look-up table forUCI multiplexing rules, a component 1110 configured to operate the UE tostored the received configuration information, a component 1130configured to operate the UE to receive the UCI request for first set ofdownlink (DL) HARQ processes via DCI on PDCCH in a later set of downlinktransmissions, a component 1132 configured to operat the UE to determinewhen to perform UCI transmission based on information, e.g. the timingindicator, included in the received UCI request, a component 1136configured to operate the UE to perform UCI transmission as perparameters including in DCI. Component 1136 includes a component 1138configured to operate the UE to transmit ACK/NACKs corresponding to theHARQ IDs in the UCI request and a component 1140 configured to operatethe UE to transmit a CSI report.

Assembly of components 1200 includes a component 1208 configured tooperate the UE to receive from the base station, e.g., a gNB,configuration information, said configuration information including setsof CG PUCCH resource and ii) a look-up table for UCI multiplexing rules,a component 1210 configured to operate the UE to stored the receivedconfiguration information, a component 1230 configured to operate the UEto receive the UCI request for first set of downlink (DL) HARQ processesvia DCI, addresses to CS-RNTI, on PDCCH in a later set of downlinktransmissions, a component 1231 configured to operate the UE todetermine when to perform UCI transmission based on information, e.g.the indicator indicating the one of the CGs, which corresponds to aconfigured set of CG OUSCH resources, included in the received UCIrequest, a component 1232 configured to operate the UE to determine UCIcontents to be transmitted in response to DCI, a component 1234configured to operate the UE to perform UCI transmission as perparameters including in DCI. Component 1234 includes a component 1236configured to operate the UE to transmit ACK/NACKs corresponding to theHARQ IDs in the UCI request, a component 11238 configured to operate theUE to transmit a scheduling request (SR), and a component 1240configured to operate the UE to transmit a CSI report.

Assembly of components 1200 further includes a component 1310 configuredto operate the UE to determine UCI contents to be transmitted inresponse to the UCI request, e.g., the UE device determines controlinformation related to channel quality or channel occupancy to multiplexand transmit with HARQ acknowledgement information in response to theUCI Request, and a component 1312 configured to operate the UE toperform UCI transmission, as per parameters including in the DCI, giventhe number of sub-bands with successful LBT. Component 1312 is furtherconfigured to add additional control information related to the qualityand/or channel occupancy of individual sub-bands constituting widebandcarrier. Component 1312 is further configured operate the UE to transmitsaid added additional control information related to the quality and/orchannel occupancy of individual sub-bands constituting wideband carrier.Component 1312 is configured to operating the UE to transmit, e.g., viaa wireless transmitter, said determined control information related tochannel quality or channel occupancy multiplexed with the determinedHARQ acknowledgement information

Numbered List of Exemplary Method Embodiments

Method Embodiment 1 A communications method, the method comprising:operating (414 or 714 or 808) a base station (gNB) to transmit an uplinkcontrol information (UCI) request (300 or 600) in a Physical DownlinkControl Channel (PDCCH) to a User Equipment (UE), said UCI requestrequesting transmission of HARQ acknowledgment information for one ormore previously communicated transmission segments identified by HARQIDs included in the UCI request and including an indication ofinformation to be multiplexed with HARQ acknowledgement information; andoperating (442 or 744) the base station to monitor for uplink controlinformation including HARQ information from the UE.

Method Embodiment 2 The communications method of Method Embodiment 1,wherein said HARQ information includes an acknowledgment (ACK) ornegative acknowledgment (NACK) corresponding to each of the identifiedHARQ IDs included in the UCI request.

Method Embodiment 3 The communications method of Method Embodiment 2,wherein said uplink control information request (300) is via downlinkcontrol information (DCI) in the Physical Downlink Control Channel(PDCCH).

Method Embodiment 4 The communications method of Method Embodiment 3,wherein said UCI request (300) is requesting the UE to transmit saidHARQ acknowledgment information in a Physical Uplink Control Channel(PUCCH) or Physical Uplink Shared Channel (PUSCH).

Method Embodiment 5 The communications method of Method Embodiment 4,further comprising: operating (412) the base station to transmit a setof HARQ processes, corresponding to said HARQ IDs, in a first channeloccupancy time (COT) (e.g., COT n); and operating (442) the base stationto receive said uplink control information including HARQ informationduring a second COT (e.g., COT n+1), said second COT being after saidfirst COT.

Method Embodiment 6 The communications method of Method Embodiment 5,wherein said transmitted UCI request and said uplink control informationincluding HARQ acknowledgment information are transmitted in unlicensedspectrum.

Method Embodiment 7 The communications method of Method Embodiment 1,wherein the HARQ IDs (302 or 618) included in the UCI request (300 or600) occupy up to 16 bits of the UCI request.

Method Embodiment 8 The communications method of Method Embodiment 1,wherein said UCI request (300) further includes a timing indicator (312)indicating which slot of an uplink channel in which the requested UCIinformation is to be transmitted.

Method Embodiment 9 The communications method of Method Embodiment 8,wherein said indication of information to be multiplexed with HARQacknowledgment information is a Channel State Information (CSI) request(304) indicating what information is to be multiplexed with HARQacknowledgment information to be communicated in response to the CSIrequest.

Method Embodiment 10 The communications method of Method Embodiment 9,wherein said CSI request (304) is an indicator including 6 or fewer bitsindicating the format and content of the information to be multiplexedwith the HARQ acknowledgment information to be communicated in a CSIreport in response to the CSI request.

Method Embodiment 11 The communications method of Method Embodiment 8,further comprising, prior to operating (414) a base station (gNB) totransmit said uplink control information (UCI) request, operating (404)the base station to configure the UE with: i) Physical Uplink ControlChannel (PUCCH) Resource Set for delayed acknowledgment/negativeacknowledgement (ACK/NACK) feedback; and ii) a look-up table for UCImultiplexing rules.

Method Embodiment 12 The communications method of Method Embodiment 2,wherein said uplink control information request (600) is via downlinkcontrol information (DCI) addressed to a Configured Scheduling—RadioNetwork Temporary Identifier (CS-RNTI) in the Physical Downlink ControlChannel (PDCCH).

Method Embodiment 13 The communications method of Method Embodiment 12,wherein said UCI request (600) is requesting the UE to transmit saidHARQ acknowledgment information in a Configured Grant Physical UplinkControl Channel (CG PUCCH) or a Configured Grant Physical Uplink SharedChannel (CG PUSCH).

Method Embodiment 14 The communications method of Method Embodiment 13,further comprising: operating (712) the base station to transmit a setof HARQ processes, corresponding to said HARQ IDs, in a first channeloccupancy time (COT)(e.g. COT n); and operating (742) the base stationto receive said uplink control information including HARQ informationduring a second COT (e.g., COT n+2), said second COT being after saidfirst COT.

Method Embodiment 15 The communications method of Method Embodiment 14,wherein said transmitted UCI request and said uplink control informationincluding HARQ acknowledgment information are transmitted in unlicensedspectrum.

Method Embodiment 16 The communications method of Method Embodiment 1,wherein said UCI request (600) further includes indicators (602) foractivation of one of a plurality of configured grants (e.g., 2 bits iffour sets of CG PUSCHs are configured to a UE).

Method Embodiment 17 The communications method of Method Embodiment 16,wherein the HARQ IDs (604) included in the UCI request (600) occupy upto 16 bits of the UCI request (600).

Method Embodiment 18 The communications method of Method Embodiment 17,wherein said UCI request (600) further includes a indication (606) ofwhether scheduling request (SR) should be reported (e.g., 1 bit).

Method Embodiment 19 The communications method of Method Embodiment 17,wherein said indication of information to be multiplexed with HARQacknowledgment information is a Channel State Information (CSI) request(608) indicating what information is to be multiplexed with HARQacknowledgment information to be communicated in response to the CSIrequest.

Method Embodiment 20 The communications method of Method Embodiment 19,wherein said CSI request (608) is an indicator including 6 or fewer bitsindicating the format and content of the information to be multiplexedwith the HARQ acknowledgment information to be communicated in a CSIreport in response to the CSI request.

Method Embodiment 21 The communications method of Method Embodiment 16,further comprising, prior to operating (714) a base station (gNB) totransmit said uplink control information (UCI) request, operating (704)the base station to configure the UE with: i) sets of Configured GrantPhysical Uplink Control Channel (CG PUCCH) Resource for delayedacknowledgment/negative acknowledgement (ACK/NACK) feedback; and ii) alook-up table for UCI multiplexing rules.

Method Embodiment 22 The communications method of Method Embodiment 1,wherein the PUCCH is on a carrier wider than 20 MHz; and wherein themethod further comprises: operating (806) the base station to performdownlink listen before talk; and wherein said UCI request requestingtransmission of HARQ acknowledgment information indicates one or moreLBT sub-bands to be used for communicating the requested information.

Method Embodiment 23 The communications method of Method Embodiment 22,further comprising: operating (810) the UE device to determine controlinformation related to channel quality or channel occupancy to multiplexand transmit with HARQ acknowledgement information in response to theUCI Request.

Method Embodiment 24 The communications method of Method Embodiment 23,further comprising: operating the UE to transmit (812) said determinedcontrol information related to channel quality or channel occupancymultiplexed with the determined HARQ acknowledgement information.

Numbered List of Exemplary Apparatus Embodiments

Apparatus Embodiment 1 A base station (e.g., gNB) (104 or 900)comprising: a wireless transmitter (914); a wireless receiver (912); anda processor (902) configured to: operate (414 or 714 or 808) the basestation (gNB) to transmit (e.g., via the wireless transmitter) an uplinkcontrol information (UCI) request (300 or 600) in a Physical DownlinkControl Channel (PDCCH) to a User Equipment (UE), said UCI requestrequesting transmission of HARQ acknowledgment information for one ormore previously communicated transmission segments identified by HARQIDs included in the UCI request and including an indication ofinformation to be multiplexed with HARQ acknowledgement information; andoperate (442 or 744 or 814) the base station to monitor for uplinkcontrol information including HARQ information from the UE.

Apparatus Embodiment 2 The base station of Apparatus Embodiment 1,wherein said HARQ information includes an acknowledgment (ACK) ornegative acknowledgment (NACK) corresponding to each of the identifiedHARQ IDs included in the UCI request.

Apparatus Embodiment 3 The base station of Apparatus Embodiment 2,wherein said uplink control information request (300) is via downlinkcontrol information (DCI) in the Physical Downlink Control Channel(PDCCH).

Apparatus Embodiment 4 The base station of Apparatus Embodiment 3,wherein said UCI request (300) is requesting the UE to transmit saidHARQ acknowledgment information in a Physical Uplink Control Channel(PUCCH) or Physical Uplink Shared Channel (PUSCH).

Apparatus Embodiment 5 The base station of Apparatus Embodiment 4,wherein said processor is further configured to: operate (412) the basestation to transmit a set of HARQ processes, corresponding to said HARQIDs, in a first channel occupancy time (COT) (e.g., COT n); and operate(442) the base station to receive said uplink control informationincluding HARQ information during a second COT (e.g., COT n+1), saidsecond COT being after said first COT.

Apparatus Embodiment 6 The base station of Apparatus Embodiment 5,wherein said transmitted UCI request and said UCI including HARQacknowledgment information are transmitted in unlicensed spectrum.

Apparatus Embodiment 7 The base station of Apparatus Embodiment 1,wherein the HARQ IDs (302 or 618) included in the UCI request (300 or600) occupy up to 16 bits of the UCI request.

Apparatus Embodiment 8 The base station of Apparatus Embodiment 1,wherein said UCI request (300) further includes a timing indicator (312)indicating which slot of an uplink channel in which the requested UCIinformation is to be transmitted.

Apparatus Embodiment 9 The base station of Apparatus Embodiment 8,wherein said indication of information to be multiplexed with HARQacknowledgment information is a Channel State Information (CSI) request(304) indicating what information is to be multiplexed with HARQacknowledgment information to be communicated in response to the CSIrequest.

Apparatus Embodiment 10 The base station of Apparatus Embodiment 9,wherein said CSI request (304) is an indicator including 6 or fewer bitsindicating the format and content of the information to be multiplexedwith the HARQ acknowledgment information to be communicated in a CSIreport in response to the CSI request.

Apparatus Embodiment 11 The base station of Apparatus Embodiment 8,wherein said processor is further configured to: operate (404) the basestation to configure the UE with: i) Physical Uplink Control Channel(PUCCH) Resource Set for delayed acknowledgment/negative acknowledgement(ACK/NACK) feedback; and ii) a look-up table for UCI multiplexing rules.prior to operating (414) a base station (gNB) to transmit said uplinkcontrol information (UCI) request, wherein said operating (404) the basestation to configure the UE being prior to said operating (414) the basestation (gNB) to transmit said uplink control information (UCI) request.

Apparatus Embodiment 12 The base station of Apparatus Embodiment 2,wherein said uplink control information request (600) is via downlinkcontrol information (DCI) addressed to a Configured Scheduling—RadioNetwork Temporary Identifier (CS-RNTI) in the Physical Downlink ControlChannel (PDCCH).

Apparatus Embodiment 13 The base station of Apparatus Embodiment 12,wherein said UCI request (600) is requesting the UE to transmit saidHARQ acknowledgment information in a Configured Grant Physical UplinkControl Channel (CG PUCCH) or a Configured Grant Physical Uplink SharedChannel (CG PUSCH).

Apparatus Embodiment 14 The base station of Apparatus Embodiment 13,wherein said processor is further configured to: operate (712) the basestation to transmit a set of HARQ processes, corresponding to said HARQIDs, in a first channel occupancy time (COT) (e.g. COT n); and operate(742) the base station to receive said uplink control informationincluding HARQ information during a second COT (e.g., COT n+2), saidsecond COT being after said first COT.

Apparatus Embodiment 15 The base station of Apparatus Embodiment 14,wherein said transmitted UCI request and said UCI including HARQacknowledgment information are transmitted in unlicensed spectrum.

Apparatus Embodiment 16 The base station of Apparatus Embodiment 1,wherein said UCI request (600) further includes indicators (602) foractivation of one of a plurality of configured grants (e.g., 2 bits iffour sets of CG PUSCHs are configured to a UE).

Apparatus Embodiment 17 The base station of Apparatus Embodiment 16,wherein the HARQ IDs (604) included in the UCI request (600) occupy upto 16 bits of the UCI request (600).

Apparatus Embodiment 18 The base station of Apparatus Embodiment 17,wherein said UCI request (600) further includes a indication (606) ofwhether scheduling request (SR) should be reported (e.g., 1 bit).

Apparatus Embodiment 19 The base station of Apparatus Embodiment 17,wherein said indication of information to be multiplexed with HARQacknowledgment information is a Channel State Information (CSI) request(608) indicating what information is to be multiplexed with HARQacknowledgment information to be communicated in response to the CSIrequest.

Apparatus Embodiment 20 The base station of Apparatus Embodiment 19,wherein said CSI request (608) is an indicator including 6 or fewer bitsindicating the format and content of the information to be multiplexedwith the HARQ acknowledgment information to be communicated in a CSIreport in response to the CSI request.

Apparatus Embodiment 21 The base station of Apparatus Embodiment 16,wherein said processor is further configured to: operate (704) the basestation to configure the UE with: i) sets of Configured Grant PhysicalUplink Control Channel (CG PUCCH) Resource for delayedacknowledgment/negative acknowledgement (ACK/NACK) feedback; and ii) alook-up table for UCI multiplexing rules, and wherein said operating(704) the base station to configure the UE prior being performed priorto said operating (714) a base station (gNB) to transmit said uplinkcontrol information (UCI) request.

Apparatus Embodiment 22 The base station of Apparatus Embodiment 1,wherein the PUCCH is on a carrier wider than 20 MHz; and wherein saidprocessor is further configured to: operate (806) the base station toperform downlink listen before talk; and wherein said UCI requestrequesting transmission of HARQ acknowledgment information indicates oneor more LBT sub-bands to be used for communicating the requestedinformation.

Numbered List of Exemplary System Embodiments

System Embodiment 1 A communications system (100) comprising: a basestation (e.g., gNB) (104 or 900) including: a wireless transmitter(914); a wireless receiver (912); and a first processor (902) configuredto: operate (414 or 714 or 808) the base station (gNB) to transmit(e.g., via the wireless transmitter) an uplink control information (UCI)request (300 or 600) in a Physical Downlink Control Channel (PDCCH) to aUser Equipment (UE), said UCI request requesting transmission of HARQacknowledgment information for one or more previously communicatedtransmission segments identified by HARQ IDs included in the UCI requestand including an indication of information to be multiplexed with HARQacknowledgement information; and operate (442 or 744 or 814) the basestation to monitor for uplink control information including HARQinformation from the UE.

System Embodiment 2 The communications system of System Embodiment 1,wherein said HARQ information includes an acknowledgment (ACK) ornegative acknowledgment (NACK) corresponding to each of the identifiedHARQ IDs included in the UCI request.

System Embodiment 3 The communications system of System Embodiment 2,wherein said uplink control information request (300) is via downlinkcontrol information (DCI) in the Physical Downlink Control Channel(PDCCH).

System Embodiment 4 The communications system of System Embodiment 3,wherein said UCI request (300) is requesting the UE to transmit saidHARQ acknowledgment information in a Physical Uplink Control Channel(PUCCH) or a Physical Uplink Shared Channel (PUSCH).

System Embodiment 5 The communications system of System Embodiment 4,wherein said first processor is further configured to: operate (412) thebase station to transmit a set of HARQ processes, corresponding to saidHARQ IDs, in a first channel occupancy time (COT) (e.g., COT n); andoperate (442) the base station to receive said uplink controlinformation including HARQ information during a second COT (e.g. COTn+1), said second COT being after said first COT.

System Embodiment 6 The communications system of System Embodiment 5,wherein said transmitted UCI request and said UCI including HARQacknowledgment information are transmitted in unlicensed spectrum.

System Embodiment 7 The communications system of System Embodiment 1,wherein the HARQ IDs (302 or 618) included in the UCI request (300 or600) occupy up to 16 bits of the UCI request.

System Embodiment 8 The communications system of System Embodiment 1,wherein said UCI request (300) further includes a timing indicator (312)indicating which slot of an uplink channel in which the requested UCIinformation is to be transmitted.

System Embodiment 9 The communications system of System Embodiment 8,wherein said indication of information to be multiplexed with HARQacknowledgment information is a Channel State Information (CSI) request(304) indicating what information is to be multiplexed with HARQacknowledgment information to be communicated in response to the CSIrequest.

System Embodiment 10 The communications system of System Embodiment 9,wherein said CSI request (304) is an indicator including 6 or fewer bitsindicating the format and content of the information to be multiplexedwith the HARQ acknowledgment information to be communicated in a CSIreport in response to the CSI request.

System Embodiment 11 The communications system of System Embodiment 8,wherein said first processor is further configured to: operate (404) thebase station to configure the UE with: i) Physical Uplink ControlChannel (PUCCH) Resource Set for delayed acknowledgment/negativeacknowledgement (ACK/NACK) feedback; and ii) a look-up table for UCImultiplexing rules, wherein said operating (404) the base station toconfigure the UE being prior to said operating (414) the base station(gNB) to transmit said uplink control information (UCI) request.

System Embodiment 12 The communications system of System Embodiment 2,wherein said uplink control information request (600) is via downlinkcontrol information (DCI) addressed to a Configured Scheduling—RadioNetwork Temporary Identifier (CS-RNTI) in the Physical Downlink ControlChannel (PDCCH).

System Embodiment 13 The communications system of System Embodiment 12,wherein said UCI request (600) is requesting the UE to transmit saidHARQ acknowledgment information in a Configured Grant Physical UplinkControl Channel (CG PUCCH) or a Configured Grant Physical Uplink SharedChannel (CG PUSCH).

System Embodiment 14 The communications system of System Embodiment 13,wherein said first processor is further configured to: operate (712) thebase station to transmit a set of HARQ processes, corresponding to saidHARQ IDs, in a first channel occupancy time (COT) (e.g., COT n); andoperate (742) the base station to receive said uplink controlinformation including HARQ information during a second COT (e.g., COTn+2), said second COT being after said first COT.

System Embodiment 15 The communications system of System Embodiment 14,wherein said transmitted UCI request and said UCI including HARQacknowledgment information are transmitted in unlicensed spectrum.

System Embodiment 16 The communications system of System Embodiment 1,wherein said UCI request (600) further includes indicators (602) foractivation of one of a plurality of configured grants (e.g., 2 bits iffour sets of CG PUSCHs are configured to a UE).

System Embodiment 17 The communications system of System Embodiment 16,wherein the HARQ IDs (604) included in the UCI request (600) occupy upto 16 bits of the UCI request (600).

System Embodiment 18 The communications system of System Embodiment 17,wherein said UCI request (600) further includes a indication (606) ofwhether scheduling request (SR) should be reported (e.g., 1 bit).

System Embodiment 19 The communications system of System Embodiment 17,wherein said indication of information to be multiplexed with HARQacknowledgment information is a Channel State Information (CSI) request(608) indicating what information is to be multiplexed with HARQacknowledgment information to be communicated in response to the CSIrequest.

System Embodiment 20 The communications system of System Embodiment 19,wherein said CSI request (608) is an indicator including 6 or fewer bitsindicating the format and content of the information to be multiplexedwith the HARQ acknowledgment information to be communicated in a CSIreport in response to the CSI request.

System Embodiment 21 The communications system of System Embodiment 16,wherein said first processor is further configured to: operate (704) thebase station to configure the UE with: i) sets of Configured GrantPhysical Uplink Control Channel (CG PUCCH) Resource for delayedacknowledgment/negative acknowledgement (ACK/NACK) feedback; and ii) alook-up table for UCI multiplexing rules, and wherein said operating(704) the base station to configure the UE prior being performed priorto said operating (714) a base station (gNB) to transmit said uplinkcontrol information (UCI) request.

System Embodiment 22 The communications system of System Embodiment 1,wherein the PUCCH is on a carrier wider than 20 MHz; and wherein saidprocessor is further configured to: operate (806) the base station toperform downlink listen before talk; and wherein said UCI requestrequesting transmission of HARQ acknowledgment information indicates oneor more LBT sub-bands to be used for communicating the requestedinformation.

System Embodiment 23 The communications system of System Embodiment 22,further comprising: said UE (110 or 1000), said UE including a secondprocessor (1002) configured to: operate (810) the UE device to determinecontrol information related to channel quality or channel occupancy tomultiplex and transmit with HARQ acknowledgement information in responseto the UCI Request.

System Embodiment 24 The communications system of System Embodiment 23,wherein said second processor (1002) is further configured to: operatethe UE to transmit (812), e.g., via wireless transmitter (1040) saiddetermined control information related to channel quality or channeloccupancy multiplexed with the determined HARQ acknowledgementinformation.

Numbered List of Exemplary Non-Transitory Computer Readable mediumEmbodiments

Non-Transitory Computer Readable medium Embodiment 1 A non-transitorycomputer readable medium (910) including computer executableinstructions which when executed by a processor (902) control a basestation (900) (e.g., gnB) (e.g., using unlicensed spectrum) to performthe steps of: operating (414 or 714 or 808) the base station (gNB) totransmit an uplink control information (UCI) request (300 or 600) in aPhysical Downlink Control Channel (PDCCH) to a User Equipment (UE), saidUCI request requesting transmission of HARQ acknowledgment informationfor one or more previously communicated transmission segments identifiedby HARQ IDs included in the UCI request and including an indication ofinformation to be multiplexed with HARQ acknowledgement information; andoperating (442 or 744) the base station to monitor for uplink controlinformation including HARQ information from the UE.

Non-Transitory Computer Readable medium Embodiment 2 A non-transitorycomputer readable medium (1020) including computer executableinstructions which when executed by a processor (1002) control a userequipment (UE) 1000 (e.g., using unlicensed spectrum) to perform thesteps of: operating (810) the UE device to determine control informationrelated to channel quality or channel occupancy to multiplex andtransmit with HARQ acknowledgement information in response to a UCIRequest, and wherein the PUCCH is on a carrier wider than 20 MHz.

The techniques of various embodiments may be implemented using software,hardware and/or a combination of software and hardware. Variousembodiments are directed to apparatus, e.g., user devices such as a userequipment (UE) device, base stations such as a gNB or ng-eNB, networknodes, an AMF device, servers, customer premises equipment devices,cable systems, network nodes, gateways, cable headend/hubsites, networkmonitoring node/servers, cluster controllers, cloud nodes, productionnodes, cloud services servers and/or network equipment devices. Variousembodiments are also directed to methods, e.g., method of controllingand/or operating user devices, base stations, gateways, servers, cablenetworks, cloud networks, nodes, servers, cloud service servers,customer premises equipment devices, controllers, network monitoringnodes/servers and/or cable or network equipment devices. Variousembodiments are also directed to machine, e.g., computer, readablemedium, e.g., ROM, RAM, CDs, hard discs, etc., which include machinereadable instructions for controlling a machine to implement one or moresteps of a method. The computer readable medium is, e.g., non-transitorycomputer readable medium.

It is understood that the specific order or hierarchy of steps in theprocesses and methods disclosed is an example of exemplary approaches.Based upon design preferences, it is understood that the specific orderor hierarchy of steps in the processes and methods may be rearrangedwhile remaining within the scope of the present disclosure. Theaccompanying method claims present elements of the various steps in asample order, and are not meant to be limited to the specific order orhierarchy presented. In some embodiments, one or more processors areused to carry out one or more steps of the each of the describedmethods.

In various embodiments each of the steps or elements of a method areimplemented using one or more processors. In some embodiments, each ofelements are steps are implemented using hardware circuitry.

In various embodiments nodes and/or elements described herein areimplemented using one or more components to perform the stepscorresponding to one or more methods, for example, message generation,message reception, signal processing, sending, comparing, determiningand/or transmission steps. Thus, in some embodiments various featuresare implemented using components or in some embodiments logic such asfor example logic circuits. Such components may be implemented usingsoftware, hardware or a combination of software and hardware. Many ofthe above described methods or method steps can be implemented usingmachine executable instructions, such as software, included in a machinereadable medium such as a memory device, e.g., RAM, floppy disk, etc. tocontrol a machine, e.g., general purpose computer with or withoutadditional hardware, to implement all or portions of the above describedmethods, e.g., in one or more nodes. Accordingly, among other things,various embodiments are directed to a machine-readable medium, e.g., anon-transitory computer readable medium, including machine executableinstructions for causing a machine, e.g., processor and associatedhardware, to perform one or more of the steps of the above-describedmethod(s). Some embodiments are directed to a device, e.g., a basestation, including a processor configured to implement one, multiple orall of the steps of one or more methods of the invention.

In some embodiments, the processor or processors, e.g., CPUs, of one ormore devices, e.g., communications nodes such as base stations or UEsare configured to perform the steps of the methods described as beingperformed by the communications nodes. The configuration of theprocessor may be achieved by using one or more components, e.g.,software components, to control processor configuration and/or byincluding hardware in the processor, e.g., hardware components, toperform the recited steps and/or control processor configuration.Accordingly, some but not all embodiments are directed to a device,e.g., communications node such as a base station or UE including, with aprocessor which includes a component corresponding to each of the stepsof the various described methods performed by the device in which theprocessor is included. In some but not all embodiments a device, e.g.,communications node, such as a base station or UE, includes a controllercorresponding to each of the steps of the various described methodsperformed by the device in which the processor is included. Thecomponents may be implemented using software and/or hardware.

Some embodiments are directed to a computer program product comprising acomputer-readable medium, e.g., a non-transitory computer-readablemedium, comprising code for causing a computer, or multiple computers,to implement various functions, steps, acts and/or operations, e.g. oneor more steps described above. Depending on the embodiment, the computerprogram product can, and sometimes does, include different code for eachstep to be performed. Thus, the computer program product may, andsometimes does, include code for each individual step of a method, e.g.,a method of operating a base station or UE. The code may be in the formof machine, e.g., computer, executable instructions stored on acomputer-readable medium, e.g., a non-transitory computer-readablemedium, such as a RAM (Random Access Memory), ROM (Read Only Memory) orother type of storage device. In addition to being directed to acomputer program product, some embodiments are directed to a processorconfigured to implement one or more of the various functions, steps,acts and/or operations of one or more methods described above.Accordingly, some embodiments are directed to a processor, e.g., CPU,configured to implement some or all of the steps of the methodsdescribed herein. The processor may be for use in, e.g., acommunications device such as a base station, a UE, a controller, orother device described in the present application. In some embodimentscomponents are implemented as hardware devices in such embodiments thecomponents are hardware components. In other embodiments components maybe implemented as software, e.g., a set of processor or computerexecutable instructions. Depending on the embodiment the componentsmaybe all hardware components, all software components, a combination ofhardware and/or software or in some embodiments some components arehardware components while other components are software components.

Numerous additional variations on the methods and apparatus of thevarious embodiments described above will be apparent to those skilled inthe art in view of the above description. Such variations are to beconsidered within the scope. Numerous additional embodiments, within thescope of the present invention, will be apparent to those of ordinaryskill in the art in view of the above description and the claims whichfollow. Such variations are to be considered within the scope of theinvention.

What is claimed is:
 1. A communications method, the method comprising:operating a base station to transmit an uplink control information (UCI)request in a Physical Downlink Control Channel (PDCCH) to a UserEquipment (UE), said UCI request requesting transmission of HARQacknowledgment information for one or more previously communicatedtransmission segments identified by HARQ IDs included in the UCI requestand including an indication of information to be multiplexed with HARQacknowledgement information; and operating the base station to monitorfor uplink control information including HARQ information from the UE.2. The communications method of claim 1, wherein the HARQ IDs includedin the UCI request occupy up to 16 bits of the UCI request.
 3. Thecommunications method of claim 1, wherein said UCI request furtherincludes a timing indicator indicating which slot of an uplink channelin which the requested UCI information is to be transmitted.
 4. Thecommunications method of claim 3, wherein said indication of informationto be multiplexed with HARQ acknowledgment information is a ChannelState Information (CSI) request indicating what information is to bemultiplexed with HARQ acknowledgment information to be communicated inresponse to the CSI request.
 5. The communications method of claim 4,wherein said CSI request is an indicator including 6 or fewer bitsindicating the format and content of the information to be multiplexedwith the HARQ acknowledgment information to be communicated in a CSIreport in response to the CSI request.
 6. The communications method ofclaim 3, further comprising, prior to operating a base station totransmit said uplink control information (UCI) request, operating thebase station to configure the UE with: i) Physical Uplink ControlChannel (PUCCH) Resource Set for delayed acknowledgment/negativeacknowledgement (ACK/NACK) feedback; and ii) a look-up table for UCImultiplexing rules.
 7. The communications method of claim 1, whereinsaid UCI request further includes indicators for activation of one of aplurality of configured grants (e.g., 2 bits if four sets of CG PUSCHsare configured to a UE).
 8. The communications method of claim 7,wherein said UCI request further includes an indication of whetherscheduling request (SR) should be reported.
 9. The communications methodof claim 8, wherein said indication of information to be multiplexedwith HARQ acknowledgement information is a Channel State Information(CSI) request indicating what information is to be multiplexed with HARQacknowledgment information to be communicated in response to the CSIrequest.
 10. The communications method of claim 7, further comprising,prior to operating a base station to transmit said uplink controlinformation (UCI) request, operating the base station to configure theUE with: i) sets of Configured Grant Physical Uplink Control Channel (CGPUCCH) Resource for delayed acknowledgment/negative acknowledgement(ACK/NACK) feedback; and ii) a look-up table for UCI multiplexing rules.11. The communications method of claim 1, wherein the PUCCH is on acarrier wider than 20 MHz; and wherein the method further comprises:operating the base station to perform downlink listen before talk; andwherein said UCI request requesting transmission of HARQ acknowledgmentinformation indicates one or more LBT sub-bands to be used forcommunicating the requested information.
 12. The communications methodof claim 11, further comprising: operating the UE device to determinecontrol information related to channel quality or channel occupancy tomultiplex and transmit with HARQ acknowledgement information in responseto the UCI Request.
 13. The communications method of claim 12, furthercomprising: operating the UE to transmit said determined controlinformation related to channel quality or channel occupancy multiplexedwith the determined HARQ acknowledgement information.
 14. A base stationcomprising: a wireless transmitter; a wireless receiver; and a processorconfigured to: operate the base station to transmit an uplink controlinformation (UCI) request in a Physical Downlink Control Channel (PDCCH)to a User Equipment (UE), said UCI request requesting transmission ofHARQ acknowledgment information for one or more previously communicatedtransmission segments identified by HARQ IDs included in the UCI requestand including an indication of information to be multiplexed with HARQacknowledgement information; and operate the base station to monitor foruplink control information including HARQ information from the UE. 15.The base station of claim 14, wherein said UCI request further includesa timing indicator indicating which slot of an uplink channel in whichthe requested UCI information is to be transmitted.
 16. The base stationof claim 15, wherein said indication of information to be multiplexedwith HARQ acknowledgment information is a Channel State Information(CSI) request indicating what information is to be multiplexed with HARQacknowledgment information to be communicated in response to the CSIrequest.
 17. The base station of claim 14, wherein said UCI requestfurther includes indicators for activation of one of a plurality ofconfigured grants.
 18. The base station of claim 17, wherein said UCIrequest further includes an indication of whether scheduling request(SR) should be reported.
 19. The base station of claim 17, wherein saidindication of information to be multiplexed with HARQ acknowledgmentinformation is a Channel State Information (CSI) request indicating whatinformation is to be multiplexed with HARQ acknowledgment information tobe communicated in response to the CSI request.
 20. The base station ofclaim 14, wherein the PUCCH is on a carrier wider than 20 MHz; andwherein said processor is further configured to: operate the basestation to perform downlink listen before talk; and wherein said UCIrequest requesting transmission of HARQ acknowledgment informationindicates one or more LBT sub-bands to be used for communicating therequested information.